Use determinate-specific input names#330
Use determinate-specific input names#330heywoodlh wants to merge 1 commit intoDeterminateSystems:mainfrom
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the
📝 WalkthroughWalkthroughThe PR updates the primary Nixpkgs input in a Nix flake configuration from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
flake.nix (1)
561-567: Documentation example references old input name.The REPL example still uses
inputs.nixpkgsbut the input has been renamed toinputs.determinate-nixpkgs. Users following this example after loading the flake will encounter an error.📝 Proposed fix
```console nix repl> :lf NixOS/nix - nix-repl> ps = lib.makeComponents { pkgs = import inputs.nixpkgs { crossSystem = "riscv64-linux"; }; } + nix-repl> ps = lib.makeComponents { pkgs = import inputs.determinate-nixpkgs { crossSystem = "riscv64-linux"; }; } nix-repl> ps
3218959 to
f1ea740
Compare
f1ea740 to
78fcfe9
Compare
Motivation
I watch my flake.lock pretty closely and don't like duplicate inputs. This renames generic inputs to something specific to Determinate -- since Determinate doesn't want users overriding nixpkgs.
Here's a snippet from my flake.nix which removes duplicate inputs:
DeterminateSystems/determinate#157 (comment)
Context
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.